Skip to content

feat(provenance): add optional DSSE export and pinned-key verification - #235

Merged
geekgonecrazy merged 4 commits into
atomicdotdev:devfrom
astrogilda:feat/provenance-dsse-export
Nov 3, 2026
Merged

geekgonecrazy merged 4 commits into
atomicdotdev:devfrom
astrogilda:feat/provenance-dsse-export

Conversation

@astrogilda

@astrogilda astrogilda commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Atomic can already hand reviewers a native PROV projection, but a DSSE-consuming reviewer has no portable signed export or pinned-key reader. This adds optional dsse-export support to provenance show and trace --json, plus an offline verify-dsse command that emits only the exact authenticated payload bytes.

The versioned container declares exporter-only coverage. It preserves existing projections and any native Data Integrity proofs, and reuses Atomic Ed25519 keys through DSSE traits with its default backend disabled. Ordinary output and native hashes/signatures stay unchanged. Export signatures do not establish original authorship, authorized action, claim truth, complete capture or verification of referenced primaries.

Validation on this head with RUSTFLAGS=-Dwarnings: 169 canonical tests and 2 doctests; 6 real CLI provenance tests with independent Python consumption and negative controls; 5 existing tests with the feature disabled; exact dedicated feature Clippy command and formatting. Feature documentation also passed with Rustdoc warnings denied. The added workflow requires the feature tests, independent Python reader and strict lint. One small shared prerequisite fix removes an existing Clippy warning in the vault context helper; the equivalent switch-path fix became obsolete after dev rewrote that code. Existing workspace CI remains unchanged.

@graywolf336
graywolf336 force-pushed the feat/provenance-dsse-export branch from b8b7188 to 8f2e2bb Compare October 23, 2026 18:16
@geekgonecrazy
geekgonecrazy merged commit 69ff296 into atomicdotdev:dev Nov 3, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants